Release 10.1A: OpenEdge Development:
ADM and SmartObjects

Performing the conversion

Progress Software Corporation strongly recommends that before you attempt a conversion as described in this section, you make a backup copy of all source files. This backup copy should be separate from and in addition to the original source files that are saved into the V8-ADM directory structure as described Step 1 below.

Press the Start Conversions button to initiate file conversion according to the sort sequence that you have established. You can convert only files whose status is shown as Not Conv.

Note: The conversion utility does not require the AppBuilder to be running because the utility converts by parsing the code; the files are not loaded into the AppBuilder. However, the application databases should be connected.

The Conversion Process

The conversion utility performs the following steps:

The utility moves the files from their current directory structure to a similar structure with a root name V8-ADM. V8-ADM is a subdirectory of the root directory originally defined in the Directory fill-in field in the upper portion of the utility window. This structure always is created; if it already exists, it is overwritten.
Note: As previously noted, it is essential that you make a backup copy of all source files before attempting a conversion.
As each file is converted, the utility changes its status from Not Conv to ..., and concludes with ###-changes.
If an error occurs during the conversion process, the utility displays an error alert box that identifies the problem and prompts you to either stop the process (that is, do not attempt to perform any more file conversions) or continue with more files. Regardless of your choice, the utility attempts to convert the file that caused the error and marks its code with an &MESSAGE statement. The statement indicates that a problem occurred during the conversion of the file and notes that the file must be adjusted manually. (Most files require some manual intervention after conversion.) This message displays each time you compile the file, flagging it as untrustworthy until you correct the problem manually.
Once the conversion is complete, the utility replaces each original file that was copied to the V8-ADM directory structure with the corresponding converted file.
Note: To abort conversion processing, press the Abort Conversions button. The conversion utility finishes processing only the current file, stopping before the next scheduled file.

Figure B–3 shows how the Conversion Utility window might look once the conversion process is complete.

Figure B–3: Conversion Utility window after a conversion

Table B–4 identifies and describes possible status labels in this window.

Table B–4: Conversion status labels displayed in the browser 

Status	Description
No-change	The file was converted, but no changes were made.
...	The conversion process is taking place.
###-changes	The file was converted and some number of changes were made. (### represents a numeric value that identifies how many conversion-related changes were made to a given file.)
Comp.Err.	After the conversion attempt, the compiler found some errors.
Version 9	The conversion utility determined that the file was either previously converted or was built as a Version 9 file, and therefore no conversion attempt was made.

Errors and the conversion utility log file

The conversion utility cannot handle all coding styles and possible code constructs. These situations require manual intervention. To facilitate this, the utility generates a log file named V89conv.log in your working directory. This log identifies what procedures were converted, approximately how many changes were made to the file, whether the file was compiled, and if the compiler encountered errors. Also, if the conversion utility determines it had difficulty converting a procedure, this log tries to capture that information and report where the problem occurred. For information on modifying the conversion utility, see the "Customizing the conversion utility" section.